View MAX66120_55637.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

19-5623; Rev 0; 11/10
KIT ATION EVALU BLE AVAILA
ISO 15693-Compliant 1Kb Memory Fob
General Description
The MAX66120 combines 1024 bits of user EEPROM, a 64-bit unique identifier (UID), and a 13.56MHz ISO 15693 RF interface in a plastic key fob. The memory is organized as 16 blocks of 8 bytes plus two more blocks for data and control registers. Each block has a userreadable write-cycle counter. Four adjacent user EEPROM blocks form a memory page (pages 0 to 3). Memory protection features are write protection and EPROM emulation, which the user can set for each individual memory page. The MAX66120 supports all ISO 15693-defined data rates, modulation indices, subcarrier modes, the selected state, application family identifier (AFI), data storage format identifier (DSFID), and the Option_flag bit for read operations. Memory write access is accomplished through standard ISO 15693 memory and control function commands.
Features
Fully Compliant with ISO 15693 and ISO 18000-3 Mode 1 Standard 13.56MHz 7kHz Carrier Frequency 1024-Bit User EEPROM with Block Lock Feature, Write-Cycle Counter, and Optional EPROMEmulation Mode 64-Bit UID Read and Write (64-Bit Block) Supports AFI and DSFID Function 10ms Programming Time To Fob: 10% or 100% ASK Modulation Using 1/4 (26kbps) or 1/256 (1.6kbps) Pulse-Position Coding From Fob: Load Modulation Using Manchester Coding with 423kHz and 484kHz Subcarrier in Low (6.6kbps) or High (26kbps) Data-Rate Mode 200,000 Write/Erase Cycles (Minimum) 40-Year Data Retention (Minimum) Compatible with Existing 1Kb ISO 15693 Products on the Market Supports the Option_Flag for Read Operations Powered Entirely Through the RF Field Operating Temperature: -25C to +50C
MAX66120
Applications
Driver Identification (Fleet Application) Access Control Asset Tracking
Ordering Information
PART MAX66120K-000AA+ TEMP RANGE -25C to +50C PIN-PACKAGE Key Fob
+Denotes a lead(Pb)-free/RoHS-compliant package.
Key Fob Mechanical Drawing appears at end of data sheet.
Typical Operating Circuit
13.56MHz READER MAGNETIC COUPLING TX_OUT IC LOAD
MAX66120
TRANSMITTER
RX_IN
ANTENNA
SWITCHED LOAD
________________________________________________________________ Maxim Integrated Products
1
For pricing, delivery, and ordering information, please contact Maxim Direct at 1-888-629-4642, or visit Maxim's website at www.maxim-ic.com.
ISO 15693-Compliant 1Kb Memory Fob MAX66120
ABSOLUTE MAXIMUM RATINGS
Maximum Incident Magnetic Field Strength ..........141.5dBA/m Operating Temperature Range ...........................-25C to +50C Relative Humidity ..............................................(Water Resistant) Storage Temperature Range ...............................-25C to +50C
Stresses beyond those listed under "Absolute Maximum Ratings" may cause permanent damage to the device. These are stress ratings only, and functional operation of the device at these or any other conditions beyond those indicated in the operational sections of the specifications is not implied. Exposure to absolute maximum rating conditions for extended periods may affect device reliability.
ELECTRICAL CHARACTERISTICS
(TA = -25C to +50C.) (Note 1)
PARAMETER EEPROM Programming Time Endurance Data Retention RF INTERFACE Carrier Frequency Activation Field Strength Write Field Strength Maximum Field Strength Power-Up Time fC HMIN HWR HMAX t POR (Notes 1, 5) At 25C (Note 2) At 25C (Note 2) At 25C (Note 2) (Notes 2, 6) 13.553 13.560 122.0 122.4 137.5 1.0 13.567 MHz dBA/m dBA/m dBA/m ms t PROG NCYCLE tRET (Note 2) At +25C (Note 3) (Note 4) 9 200,000 40 10 ms Cycles Years SYMBOL CONDITIONS MIN TYP MAX UNITS
System requirement. Guaranteed by simulation; not production tested. Write-cycle endurance is degraded as TA increases. Not 100% production tested; guaranteed by reliability monitor sampling. Guaranteed by 100% production test at elevated temperature for a shorter time; equivalence of this production test to data sheet limit at operating temperature range is established by reliabiliity testing. Note 5: Production tested at 13.56MHz only. Note 6: Measured from the time at which the incident field is present with strength greater than or equal to H(MIN) to the time at which the MAX66120's internal power-on reset signal is deasserted and the device is ready to receive a command frame. Not characterized or production tested; guaranteed by simulation only. Note 1: Note 2: Note 3: Note 4:
Detailed Description
The MAX66120 combines 1024 bits of user EEPROM, 128 bits of user and control registers, a 64-bit unique identifier (UID), and a 13.56MHz ISO 15693 RF interface in a single key fob. The memory is organized as 18 blocks of 8 bytes each. Each block has a user-readable write-cycle counter. Four adjacent user EEPROM blocks form a memory page (pages 0 to 3). Memory protection features include write protection and EPROM emulation, which the user can set for each individual memory page. The memory of the MAX66120 is accessed through the standard ISO 15693 memory and control function commands. The data rate can be as high as 26.69kbps. The MAX66120 supports AFI and DSFID. Applications of the MAX66120 include driver identification (fleet application), access control, and asset tracking.
Overview
Figure 1 shows the relationships between the major control and memory sections of the MAX66120. The device has three main data components: 1) 64-bit UID, 2) four 256-bit pages of user EEPROM, and 3) two 8byte blocks of user and control registers. Figure 2 shows the applicable ISO 15693 commands and their purpose. The network function commands allow the master to identify all slaves in its range and to change their state, e.g., to select one for further communication. The protocol required for these network function commands is described in the Network Function Commands section. The memory and control functions access the memory of the MAX66120 for reading and writing. The protocol for these memory and control function commands is described in the Memory and Control Function Commands section. All data is read and written least significant bit (LSb) first, starting with the least significant byte (LSB).
2
_______________________________________________________________________________________
ISO 15693-Compliant 1Kb Memory Fob MAX66120
INTERNAL SUPPLY VOLTAGE REGULATOR
RF FRONTEND
ISO 15693 FRAME FORMATTING AND ERROR DETECTION
MEMORY AND FUNCTION CONTROL
UID
DATA fc
MODULATION
REGISTER BLOCK
USER EEPROM
Figure 1. Block Diagram
MAX66120
COMMAND TYPE: NETWORK FUNCTION COMMANDS AVAILABLE COMMANDS: INVENTORY STAY QUIET SELECT RESET TO READY GET SYSTEM INFORMATION WRITE SINGLE BLOCK LOCK BLOCK READ SINGLE BLOCK READ MULTIPLE BLOCKS CUSTOM READ BLOCK WRITE AFI LOCK AFI WRITE DSFID LOCK DSFID DATA FIELD AFFECTED: UID, AFI, DSFID, ADMINISTRATIVE DATA UID UID UID UID, AFI, DSFID, CONSTANTS UID, DATA OF SELECTED MEMORY BLOCK, APPLICABLE PROTECTION CONTROL REGISTER UID, APPLICABLE PROTECTION CONTROL REGISTER UID, SELECTED MEMORY BLOCK, APPLICABLE PROTECTION CONTROL REGISTER UID, SELECTED MEMORY BLOCK, APPLICABLE PROTECTION CONTROL REGISTER MFGCODE, UID, SELECTED MEMORY BLOCK, APPLICABLE PROTECTION CONTROL REGISTER, INTEGRITY BYTES UID, AFI BYTE UID, AFI LOCK BYTE UID, DSFID BYTE UID, DSFID LOCK BYTE
MEMORY AND CONTROL FUNCTION COMMANDS
Figure 2. ISO 15693 Commands Overview
MSb 64 E0h 57 56 2Bh 49 48 0h 45 44 FEATURE CODE (02h) 37 36
LSb 1 36-BIT IC SERIAL NUMBER
Figure 3. 64-Bit UID
Parasite Power
As a wireless device, the MAX66120 is not connected to any power source. It gets the energy for operation from the surrounding RF field, which must have a minimum strength as specified in the Electrical Characteristics table.
Unique Identification Number (UID)
Each MAX66120 contains a factory-programmed and locked identification number that is 64 bits long (Figure 3). The lower 36 bits are the serial number of the chip. The next 8 bits store the device feature code, which is 02h. Bits 45 to 48 are 0h. The code in
3
_______________________________________________________________________________________
ISO 15693-Compliant 1Kb Memory Fob MAX66120
BLOCK NUMBER 0 00h 01h 02h 03h 04h 05h 06h 07h 08h 09h 0Ah 0Bh 0Ch 0Dh 0Eh 0Fh 10h 11h U1 BP1 U2 BP2 U3 BP3 DATA BYTE NUMBER (SEQUENCE LEFT TO RIGHT AS WRITTEN TO OR READ FROM DEVICE) 1 2 3 4 5 6 7 Page 0 User EEPROM R/(W) Page 0 User EEPROM R/(W) Page 0 User EEPROM R/(W) Page 0 User EEPROM R/(W) Page 1 User EEPROM R/(W) Page 1 User EEPROM R/(W) Page 1 User EEPROM R/(W) Page 1 User EEPROM R/(W) Page 2 User EEPROM R/(W) Page 2 User EEPROM R/(W) Page 2 User EEPROM R/(W) Page 2 User EEPROM R/(W) Page 3 User EEPROM R/(W) Page 3 User EEPROM R/(W) Page 3 User EEPROM R/(W) Page 3 User EEPROM R/(W) U4 BP4 AFI U-Lock DSFID AFI-Lock U5 DSFIDLock U6 S-Lock INTEGRITY BYTES LSB MSB
Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter Write-Cycle Counter
Figure 4. Memory Map
bit locations 49 to 56 identifies the chip manufacturer, according to ISO/IEC 7816-6/AM1. This code is 2Bh for Maxim. The code in the upper 8 bits is E0h. The UID is read accessible through the Inventory and Get System Information commands.
Detailed Memory Description
The memory of the MAX66120 is organized as 18 blocks of 8 bytes each. Figure 4 shows the memory map. The first 16 blocks (block numbers 00h to 0Fh in hexadecimal counting) are the user EEPROM, the area for application-specific data. Four adjacent blocks are also referred to as a page. Blocks 00h to 03h are page 0, blocks 04h to 07h are page 1, blocks 08h to 0Bh are page 2, and blocks 0Ch to 0Fh are page 3. Block 10h provides storage for user-programmable parameters that are defined by the ISO 15693 standard. These are AFI and DSFID. The remaining bytes (U1 to U6) are not defined by the communication standard; the application software can use them, e.g., for
proprietary markings. Block 11h contains control bytes that determine the operation of the individual pages (EPROM-emulation mode or write protection of individual blocks), or to write protect U1 to U4, the AFI, and the DSFID byte. The S-Lock byte, if programmed to a suitable code, only protects itself from future changes. The self-protection feature can be used to permanently mark the fob as being "special," as defined by the application. Table 1 illustrates the relationship between the controlling register in block 11h and the memory area affected. Tables 2 and 3 specify the code assignments to achieve the protection. Besides the storage for 8 data bytes, each memory block has 2 integrity bytes, which are not memory mapped. The integrity bytes function as a MAX66120maintained, 16-bit write-cycle counter. Having reached its maximum value of 65,535, the write-cycle counter stops incrementing, but does not prevent additional write cycles to the memory block. The integrity bytes can be read through the Custom Read Block command.
4
_______________________________________________________________________________________
ISO 15693-Compliant 1Kb Memory Fob
Table 1. Memory Protection Matrix
AFFECTED MEMORY AREA CONTROLLING REGISTER* BP1 BP2 BP3 BP4 U-Lock AFI-Lock DSFID-Lock S-Lock BLOCKS 00h TO 03h E, W -- -- -- -- -- -- -- BLOCKS 04h TO 07h -- E, W -- -- -- -- -- -- BLOCKS BLOCKS 08h TO 0Bh 0Ch TO 0Fh -- -- E, W -- -- -- -- -- -- -- -- E, W -- -- -- -- U1 TO U4 -- -- -- -- W -- -- -- AFI -- -- -- -- -- W -- -- DSFID -- -- -- -- -- -- W -- S-LOCK -- -- -- -- -- -- -- W
MAX66120
*If programmed to a locking (protecting) code, the controlling register irreversibly protects itself from further changes. See Tables 2 and 3 for additional details.
Legend for Table 1:
CODE E W DESCRIPTION ERPOM-Emulation Mode Write Protection
Table 2. BP1 to BP4 Protection Code Assignments
CODE 00000000b (00h) Unlocked (factory default) EPROM-Emulation Mode (irreversible) BP1: blocks 00h to 03h BP2: blocks 04h to 07h BP3: blocks 08h to 0Bh BP4: blocks 0Ch to 0Fh Write-Protect Block Mode. Once set to Ah, the upper nibble cannot be changed to any other value (irreversible). The bits of the lower nibble can still be changed only from 0 (unlocked) to 1 (locked) to write protect blocks individually. b0: block 00h (BP1), block 04h (BP2), block 08h (BP3), block 0Ch (BP4) b1: block 01h (BP1), block 05h (BP2), block 09h (BP3), block 0Dh (BP4) b2: block 02h (BP1), block 06h (BP2), block 0Ah (BP3), block 0Eh (BP4) b3: block 03h (BP1), block 07h (BP2), block 0Bh (BP3), block 0Fh (BP4) DESCRIPTION
00001010b (0Ah)
1010b (Axh)
Note: Do not program the upper nibble of BP4 to 9 or 5, because this blocks the read access to blocks 0Ch to 0Fh.
_______________________________________________________________________________________
5
ISO 15693-Compliant 1Kb Memory Fob MAX66120
Table 3. Protection Code Assignments for U-Lock, AFI-Lock, DSFID-Lock, S-Lock
CODE 00000000b (00h) 10101010b (AAh) All other codes Unlocked (factory default) Locked (irreversible) Unlocked DESCRIPTION
SOF
1 OR MORE DATA BYTES
CRC (LSB)
CRC (MSB)
EOF TIME
Figure 5. ISO 15693 Frame Format
CARRIER AMPLITUDE
100%
t
Figure 6. Downlink Modulation (e.g., Approximately 100% Amplitude Modulation)
ISO 15693 Communication Concept
The communication between the master and the MAX66120 (slave) is based on the exchange of data packets. The master initiates every transaction; only one side (master or slaves) transmits information at any time. Each data packet begins with a start-of-frame (SOF) pattern and ends with an end-of-frame (EOF) pattern. A data packet with at least 3 bytes between SOF and EOF is called a frame (Figure 5). The last 2 bytes of an ISO 15693 frame are an inverted 16-bit
CRC of the preceding data generated according to the CRC-16-CCITT polynomial. This CRC is transmitted with the LSB first. For more details on the CRC-16-CCITT, refer to ISO 15693 Part 3, Annex C. For transmission, the frame information is modulated on a carrier frequency, which is 13.56MHz for ISO 15693. The subsequent paragraphs are a concise description of the required modulation and coding. For full details including graphics of the data coding schemes and SOF/EOF timing, refer to ISO 15693-2, Sections 7.2, 7.3, and 8.
6
_______________________________________________________________________________________
ISO 15693-Compliant 1Kb Memory Fob MAX66120
PULSEMODULATED CARRIER ~ 9.44s ~ 18.88s
01234
.
.
.
.
.
2 2 5
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2222 5555 2345
~ 4.833ms
Figure 7. Downlink Data Coding (Case "1 Out of 256")
The path from master to slave uses amplitude modulation (Figure 6); the modulation index can be either in the range of 10% to 30% or 100% (ISO 15693-2, Section 7.1). The standard defines two pulse-position coding schemes that must be supported by a compliant device. Scheme A uses the "1 out of 256" method (Figure 7), where the transmission of 1 byte takes 4.833ms, equivalent to a data rate of 1655bps. The location of a modulation notch during the 4.833ms conveys the value of the byte. Scheme B uses the "1 out of 4" method (Figure 8), where the transmission of 2 bits takes 75.52s, equivalent to a data rate of 26,484bps. The location of a modulation notch during the 75.52s conveys the value of the 2 bits. A byte is transmitted as a concatenation of four 2-bit transmissions, with the least significant 2 bits of the byte being transmitted first. The transmission of the SOF pattern takes the same time as transmitting 2 bits in Scheme B. The SOF pattern has two modulation notches, which makes it distinct from any 2-bit pattern. The position of the second notch tells whether the frame uses the "1 out of 256" or "1 out of 4" coding scheme (Figures 9 and 10, respectively). The transmission of the EOF pattern takes 37.76s; the EOF is the same for both coding schemes and has one modulation notch (Figure 11). The path from slave to master uses one or two subcarriers, as specified by the Subcarrier_flag bit in the request data packet. The standard defines two data rates for the response, low (approximately 6600bps) and high (approximately 26,500bps). The Data_rate_flag bit in the
request data packet specifies the response data rate. The data rate varies slightly depending on the use of one or two subcarriers. The LSb is transmitted first. A compliant device must support both subcarrier modes and data rates. In the single subcarrier case, the subcarrier frequency is 423.75kHz. One bit is transmitted in 37.76s (high data rate) or 151s (low data rate). The modulation is the on/off key. For a logic 0, the subcarrier is on during the first half of the bit transmission time and off for the second half. For a logic 1, the subcarrier is off during the first half of the bit transmission time and on for the second half. See Figure 12 for more details. In the two subcarrier cases, the subcarrier frequencies are 423.75kHz and 484.28kHz. The bit duration is the same as in the single subcarrier case. The modulation is equivalent to binary FM. For a logic 0, the lower subcarrier is on during the first half of the bit transmission time, switching to the higher subcarrier for the second half. For a logic 1, the higher subcarrier is on during the first half of the bit transmission time, switching to the lower subcarrier for the second half. See Figure 13 for details. The transmission of the SOF pattern takes the same time as transmitting 4 bits (approximately 151s at a high data rate or approximately 604s at a low data rate). The SOF is distinct from any 4-bit data sequence. The EOF pattern is equivalent to a SOF being transmitted backwards. The exact duration of the SOF and EOF varies slightly depending on the use of one or two subcarriers (see Figures 14 and 15, respectively).
_______________________________________________________________________________________
7
ISO 15693-Compliant 1Kb Memory Fob MAX66120
PULSE POSITION "00"
~ 9.44s
~ 9.44s ~ 75.52s
PULSE POSITION "01" (1 = LSb)
~ 28.32s
~ 9.44s ~ 75.52s
PULSE POSITION "10" (0 = LSb)
~ 47.20s ~ 75.52s PULSE POSITION "11"
~ 9.44s
~ 66.08s ~ 75.52s
~ 9.44s
Figure 8. Downlink Data Coding (Case "1 Out of 4") (Carrier Not Shown)
~ 9.44s ~ 37.76s ~ 37.76s
~ 9.44s
Figure 9. Downlink SOF for "1 Out of 256" Coding (Carrier Not Shown)
8
_______________________________________________________________________________________
ISO 15693-Compliant 1Kb Memory Fob MAX66120
~ 9.44s ~ 37.76s
~ 9.44s
~ 9.44s ~ 37.76s
Figure 10. Downlink SOF for "1 Out of 4" Coding (Carrier Not Shown)
~ 9.44s ~ 37.76s
~ 9.44s
Figure 11. Downlink EOF (Identical for Both Coding Schemes) (Carrier Not Shown)
TRANSMITTING A ZERO
423.75kHz, ~ 18.88s
~ 18.88s
~ 37.76s
TRANSMITTING A ONE
~ 18.88s
423.75kHz, ~ 18.88s
~ 37.76s
Figure 12. Uplink Coding, Single Subcarrier Case (High Data-Rate Timing)
_______________________________________________________________________________________
9
ISO 15693-Compliant 1Kb Memory Fob MAX66120
423.75kHz, ~ 18.88s
484.28kHz, ~ 18.58s TRANSMITTING A ZERO ~ 37.46s
484.28kHz, ~ 18.58s
423.75kHz, ~ 18.88s TRANSMITTING A ONE ~ 37.46s
Figure 13. Uplink Coding, Two Subcarriers Case (High Data-Rate Timing)
423.75kHz
423.75kHz
~ 56.64s
~ 56.64s
~ 37.76s
Figure 14. Uplink SOF, Single Subcarrier Case (High Data-Rate Timing)
484.28kHz
423.75kHz
484.28kHz
423.75kHz
~ 55.75s
~ 56.64s
~ 37.46s
Figure 15. Uplink SOF, Two Subcarriers Case (High Data-Rate Timing)
10
______________________________________________________________________________________
ISO 15693-Compliant 1Kb Memory Fob
ISO 15693 Slave States and Address Modes
Initially, the master has no information whether there are any RF devices in the field of its antenna. The master learns the UIDs of the slaves in its field from the responses to the Inventory command, which does not use the Address_flag and the Select_flag bits. The state transitions are controlled by network function commands. Figure 16 shows details. ISO 15693 defines four states in which a slave can be plus three address modes. The states are power-off, ready, quiet, and selected. The address modes are nonaddressed, addressed, and selected. The addressed mode requires that the master include the slave's UID in the request, which increases the size of the requests by 8 bytes. Table 4 shows which address mode is applicable depending on the slave's state and how to set the Address_flag and the Select_flag bits for each address mode. ready state and transition to the quiet or the selected state upon receiving the Stay Quiet or Select command sent in the addressed mode.
MAX66120
Quiet State In this state, a slave has enough power to perform any of its functions. The purpose of the quiet state is to silence slaves that the master does not want to communicate with. Only commands sent with the addressed mode are accepted and processed. This way the master can use the nonaddressed mode for communication with remaining slaves in the ready state, which minimizes the size of the request data packets. As long as no additional slaves arrive in the RF field, it is safe for the master to continue communicating in the nonaddressed mode. A slave can exit the quiet state and transition to the ready or the selected state upon receiving the Reset to Ready or Select command sent in the addressed mode. Selected State In this state, a slave has enough power to perform any of its functions. The purpose of the selected state is to isolate the slave that the master wants to communicate with. Commands are accepted and processed regardless of the address mode in which they are sent, including the Inventory command. With multiple slaves in the RF field, the master can put one slave in the selected state and leave all the others in the ready state. This method requires less communication than using the quiet state to single out the slave for communication. For a slave in the selected state, the master can use the selected mode, which keeps the request data packets as short as with the nonaddressed mode. A new slave entering the RF field cannot disturb the communication, since it stays in the ready state. A slave can exit the
ISO 15693 States and Transitions
Power-Off State This state applies if the slave is outside the master's RF field. A slave transitions to the power-off state when leaving the power-delivering RF field. When entering the RF field, the slave automatically transitions to the ready state. Ready State In this state, a slave has enough power to perform any of its functions. The purpose of the ready state is to have the slave population ready to process the inventory command as well as other commands sent in the addressed or nonaddressed mode. A slave can exit the
Table 4. Slave States and Applicable Address Modes
ADDRESS MODES SLAVE STATES Power-Off Ready Quiet Selected NONADDRESSED MODE (Address_flag = 0; Select_flag = 0) (Inactive) Yes No Yes ADDRESSED MODE (Address_flag = 1; Select_flag = 0) (Inactive) Yes Yes Yes SELECTED MODE (Address_flag = 0; Select_flag = 1) (Inactive) No No Yes
______________________________________________________________________________________
11
ISO 15693-Compliant 1Kb Memory Fob MAX66120
RESPONSE LEGEND: RESPONSE TO RESET TO READY RESPONSE TO SELECT NO RESPONSE POWER-OFF ADDRESS MODE LEGEND: [N] NONADDRESSED [A] ADDRESSED [S] SELECTED
OUT OF FIELD
IN FIELD
NOTE 1 OUT OF FIELD READY OUT OF FIELD
RESET TO READY [A] MATCHING UID
RESET TO READY [N, A, S] SELECT [A] MATCHING UID STAY QUIET [A] MATCHING UID STAY QUIET [A] MATCHING UID SELECT [A], NONMATCHING UID
QUIET SELECT [A] MATCHING UID NOTE 2
SELECTED
NOTE 3
NOTE 1: THE SLAVE PROCESSES THE INVENTORY COMMAND AND OTHER COMMANDS PROVIDED THAT THEY ARE SENT IN THE [N] OR [A] ADDRESS MODE. NOTE 2: THE SLAVE PROCESSES ONLY COMMANDS SENT IN THE [A] ADDRESS MODE. NOTE 3: THE SLAVE PROCESSES THE INVENTORY COMMAND AND OTHER COMMANDS IN ANY ADDRESS MODE.
Figure 16. ISO 15693 State Transitions Diagram
selected state and transition to the ready or the quiet state upon receiving the Reset to Ready command sent in any address mode or the Stay Quiet command sent in the addressed mode. A slave also transitions from selected to ready upon receiving a Select command if the UID in the request is different from the slave's own UID. In this case the master's intention is to transition
another slave with the matching UID to the selected state. If the slave already in the selected state does not recognize the command, e.g., due to a bit error, two slaves could be in the selected state. To prevent this from happening, the master should use the Reset to Ready or the Stay Quiet command to transition a slave out of the selected state.
12
______________________________________________________________________________________
ISO 15693-Compliant 1Kb Memory Fob
Request Flags, Inventory_flag Bit Not Set
BIT 8 (MSb) 0 BIT 7 Option_flag BIT 6 Address_flag BIT 5 Select_flag BIT 4 0 BIT 3 BIT 2 BIT 1 (LSb) Inventory_flag Data_rate_flag Subcarrier_flag (= 0)
MAX66120
Request Flags, Inventory_flag Bit Set
BIT 8 (MSb) 0 BIT 7 0 BIT 6 Nb_slots_flag BIT 5 AFI_flag BIT 4 0 BIT 3 BIT 2 BIT 1 (LSb) Inventory_flag Data_rate_flag Subcarrier_flag (= 1)
Request Flags
The command descriptions on the subsequent pages begin with a byte called request flags. The ISO 15693 standard defines two formats for the request flags byte. The state of the Inventory_flag bit controls the function of the bits in the upper half of the request flags byte. The function of the request flags byte is as follows.
Bit 1: Subcarrier Flag (Subcarrier_flag). This bit specifies whether the response data packet is transmitted using a single subcarrier (bit = 0) or two subcarriers (bit = 1).
Inventory_flag Bit Set
Bits 8, 7, 4: No Function. These bits have no function. They must be transmitted as 0. Bit 6: Slot Counter Flag (Nb_slots_flag). This bit specifies whether the command is processed using a slot counter (bit = 0) or without using the slot counter (bit = 1). Bit 5: Application Family Identifier Flag (AFI_flag). To detect only slaves with a certain AFI value, the AFI_flag bit must be 1 and the desired AFI value must be included in the request. If the least significant nibble of the AFI in the request is 0000b, slaves process the command only if the most significant nibble of the AFI matches. If the AFI in the request is 00h, all slaves process the command regardless of their AFI. Bit 3: Inventory Flag (Inventory_flag). This bit must be 1 for the Inventory command only. For all other commands, this bit must be 0. Bit 2: Data Rate Flag (Data_rate_flag). This bit specifies whether the response data packet is transmitted using the low data rate (bit = 0) or the high data rate (bit = 1). Bit 1: Subcarrier Flag (Subcarrier_flag). This bit specifies whether the response data packet is transmitted using a single subcarrier (bit = 0) or two subcarriers (bit = 1).
Inventory_flag Bit Not Set
Bits 8, 4: No Function. These bits have no function. They must be transmitted as 0. Bit 7: Options Flag (Option_flag). This bit is used with block read commands to include the block security status in the response. If not applicable for a command, the Option_flag bit must be 0. Bit 6: Address Flag (Address_flag). This bit specifies whether all slaves in the master's field that are in the selected or ready state process the request (bit = 0) or only the single slave whose UID is specified in the request (bit = 1). If the Address_flag bit is 0, the request must not include a UID. The combination of both the Select_flag and Address_flag bits being set (= 1) is not valid. Bit 5: Select Flag (Select_flag). This bit specifies whether the request is processed only by the slave in the selected state (bit = 1) or by any slave according to the setting of the Address_flag bit (bit = 0). Bit 3: Inventory Flag (Inventory_flag). This bit must be 1 for the Inventory command only. For all other commands, this bit must be 0. Bit 2: Data Rate Flag (Data_rate_flag). This bit specifies whether the response data packet is transmitted using the low data rate (bit = 0) or the high data rate (bit = 1).
______________________________________________________________________________________
13
ISO 15693-Compliant 1Kb Memory Fob MAX66120
Request Data for the Inventory Command
REQUEST FLAGS (1 Byte) COMMAND 01h AFI (NOTE 1) (1 Byte) MASK LENGTH (1 Byte) MASK PATTERN (NOTE 2) (Up to 8 Bytes)
Note 1: The AFI byte is transmitted only if the AFI_flag bit is set to 1. The AFI byte, if transmitted, narrows the range of slaves that qualify for responding to the request. Note 2: The mask pattern is transmitted only if the selection mask length is not 0. If the mask length is not an integer multiple of 8, the MSB of the mask pattern must be padded with 0 bits. The LSb of the mask pattern is transmitted first.
Response Data for the Inventory Command (No Error)
RESPONSE FLAGS 00h DSFID (1 Byte) UID (8 Bytes)
Network Function Commands
The command descriptions show the data fields of the request and response data packets. To create the complete frame, an SOF, 16-bit CRC, and EOF must be added (see Figure 5). The ISO 15693 standard defines four network function commands: Inventory, Stay Quiet, Select, and Reset to Ready. This section describes the format of the request and response data packets.
cessing of an Inventory command ends when the master sends the SOF of a new frame. Response data for the Inventory command (no error) is transmitted only if a slave qualifies to respond. In case of an error in the request, slaves do not respond. When receiving the Inventory command, the slave devices in the RF field enter the collision management sequence. If a slave meets the conditions to respond, it sends out a response data packet. If multiple slaves qualify, e.g., AFI, mask, and slot counter are not used, the response frames collide and are not readable. To receive readable response frames with the UID and DSFID, the master must eliminate the collision. Not knowing the slave population, the master could begin with a mask length of 0 and activate the slot counter. By using this method and going through all 16 slots, the master has a chance to receive clean responses (i.e., the slave is identified) as well as colliding responses. To prevent a slave that has been identified from further participating in the collision management sequence, the master transitions it to the quiet state. Next, the master issues another Inventory command where the slot number that previously generated a collision is now used as a 4-bit mask, and runs again through all 16 slots. If a collision is found, another inventory command is issued, this time with a mask that is extended at the higher bits by the slot counter value that produced the collision. This process is repeated until all slaves are identified. For a full description of the Inventory request processing by the slave device and the timing specifications, refer to ISO 15693 Part 3, Sections 8 and 9.
Inventory
The Inventory command allows the master to learn the UIDs and DSFIDs of all slaves in its RF field in an iterative process. It is the only command for which the Inventory_flag bit must be 1. The Inventory command uses two command-specific parameters, which are the mask length and the mask pattern. The mask allows the master to preselect slaves for responding to the Inventory command. The LSb of the mask aligns with the LSb of the slave's UID. The master can choose not to use a mask, in which case all slaves qualify, provided they are not excluded by the AFI criteria (see the Request Flags section). The maximum mask length is 60 (3Ch, if Nb_slots_flag = 0) or 64 (40h, if Nb_slots_flag = 1). The mask pattern defines the least significant bits (as many as specified by the mask length) that a slave's UID must match to qualify for responding to the Inventory command (case Nb_slots_flag = 1). If the slot counter is used (Nb_slots_flag = 0), the value of the slot counter extends the mask pattern at the higher bits for comparison to the slave's UID. The slot counter starts at 0 after the inventory request frame is transmitted and increments during the course of the Inventory command with every subsequent EOF sent by the master. The pro-
14
______________________________________________________________________________________
ISO 15693-Compliant 1Kb Memory Fob
Request Data for the Stay Quiet Command
REQUEST FLAGS (1 Byte) COMMAND 02h UID (8 Bytes)
MAX66120
Request Data for the Select Command*
REQUEST FLAGS (1 Byte) COMMAND 25h UID (8 Bytes)
*If this command is processed without any error, the slave responds with a response flags byte of 00h.
Request Data for the Reset to Ready Command*
REQUEST FLAGS (1 Byte) COMMAND 26h UID** (8 Bytes)
*If this command is processed without any error, the slave responds with a response flags byte of 00h. **The UID is transmitted only in the addressed mode.
Stay Quiet
The Stay Quiet command addresses an individual slave and transitions it to the quiet state. The request must be sent in the addressed mode (Select_flag bit = 0, Address_flag bit = 1). The slave transitioning to the quiet state does not send a response.
Memory and Control Function Commands
The command descriptions show the data fields of the request and response data packets. To create the complete frame, an SOF, 16-bit CRC, and EOF must be added (see Figure 5). ISO 15693 defines three address modes, selected, addressed, and nonaddressed, which are specified through the setting of the Select_flag bit and the Address_flag bit. The memory and control function commands can be issued in any address mode. To access slaves in the quiet state, the addressed mode is required. The addressed mode requires that the master include the slave's UID in the request.
Select
The Select command addresses an individual slave and transitions it to the selected state. The request must be sent in the addressed mode (Select_flag bit = 0, Address_flag bit = 1). The slave transitioning to the selected state sends a response. If there was a slave with a different UID in the selected state, then that slave transitions to the ready state without sending a response.
Reset to Ready
The Reset to Ready command addresses an individual slave and transitions it to the ready state. To address a slave in the quiet state, the request must be sent in the addressed mode (Select_flag bit = 0, Address_flag bit = 1). To address a slave in the selected state, the request can be sent in any address mode. The slave transitioning to the ready state sends a response.
Error Indication
Depending on the complexity of a function, various error conditions can occur. In case of an error, the response to a request begins with a response flags byte 01h followed by one 1-byte error code. Table 5 shows a matrix of commands and potential errors. If there was no error, the response begins with a response flags byte 00h followed by command-specific data, as specified in the detailed command description. If the MAX66120 does not recognize a command, it does not generate a response.
______________________________________________________________________________________
15
ISO 15693-Compliant 1Kb Memory Fob MAX66120
Table 5. Error Code Matrix
FAILING COMMANDS Read Multiple Blocks Write Single Block Write DSFID (1 Byte) Read Single Block ERROR CODE Lock DSFID Get System Information Custom Read Block Lock Block Write AFI UID (8 Bytes) Lock AFI
ERROR DESCRIPTION
Invalid block number Already locked Write access failed because block is locked
10h 11h 12h
Detailed Command Descriptions
In the request data graphics of this section, the UID field is shaded to indicate that the inclusion of the UID depends on the address mode.
Get System Information
The Get System Information command allows the master to retrieve technical information about the MAX66120. The IC reference code indicates the die revision in hexadecimal format, such as A1h, A2h, B1h, etc.
Write Single Block
The normal way to write data to the device is through the Write Single Block command. This command uses
one command-specific parameter, which is the memory block number. Valid block numbers are 00h to 11h. Writing a block takes tPROG. The response is transmitted after the memory is updated. Depending on the protection settings of the memory location to be updated, the MAX66120 manipulates data as it arrives in a buffer. Upon receiving a Write Single Block request for a write-protected location (e.g., a self-locking nibble or byte in memory block 11h), the buffer is loaded with the data already in memory, rather than the data transmitted in the request. Similarly, if the target memory block is in EPROM mode, the buffer is loaded with the bitwise logical AND of the transmitted data and data already in memory. In all other cases, the data sent by the master arrives in the buffer unaltered.
Request Data for the Get System Information Command
REQUEST FLAGS (1 Byte) COMMAND 2Bh
Response Data for the Get System Information Command (No Error)
RESPONSE FLAGS 00h INFO FLAGS 0Fh UID (8 Bytes) DSFID (1 Byte) AFI (1 Byte) NUMBER OF BLOCKS 12h MEMORY BLOCK SIZE 07h IC REFERENCE
Request Data for the Write Single Block Command*
REQUEST FLAGS (1 Byte) COMMAND 21h UID (8 Bytes) BLOCK NUMBER (1 Byte) NEW BLOCK DATA (8 Bytes)
*If this command is processed without any error, the slave responds with a response flags byte of 00h.
16
______________________________________________________________________________________
ISO 15693-Compliant 1Kb Memory Fob
Request Data for the Lock Block Command*
REQUEST FLAGS (1 Byte) COMMAND 22h UID (8 Bytes) BLOCK NUMBER (1 Byte)
MAX66120
*If this command is processed without any error, the slave responds with a response flags byte of 00h.
Request Data for the Read Single Block Command
REQUEST FLAGS (1 Byte) COMMAND 20h UID (8 Bytes) BLOCK NUMBER (1 Byte)
Response Data for the Read Single Block Command (No Error, Option_flag Not Set)
RESPONSE FLAGS 00h MEMORY DATA (8 Bytes)
Response Data for the Read Single Block Command (No Error, Option_flag Set)
RESPONSE FLAGS 00h SECURITY STATUS (1 Byte) MEMORY DATA (8 Bytes)
Legend:
CODE 00h 01h The memory block is not protected. The memory block is write protected. SECURITY STATUS CODE EXPLANATION
Lock Block
The Lock Block command permanently locks (write protects) the selected block and reports the success of the operation in the response. Locking a block takes tPROG. The response is transmitted after the protection byte is updated. The block protection can alternatively be achieved by direct writing to memory block 11. Before using the Lock Block command, the final block data should be defined and written to the device.
Read Single Block
The Read Single Block command allows for retrieving the data of a single memory block. This command uses one command-specific parameter, which is the memory block number. Valid block numbers are 00h to 11h. If the Option_flag bit is set, the response includes the block's security status.
______________________________________________________________________________________
17
ISO 15693-Compliant 1Kb Memory Fob MAX66120
Request Data for the Read Multiple Blocks Command
REQUEST FLAGS (1 Byte) COMMAND 23h UID (8 Bytes) STARTING BLOCK NUMBER (1 Byte) NUMBER OF BLOCKS (1 Byte)
Response Data for the Read Multiple Blocks Command (No Error, Option_flag Not Set)
RESPONSE FLAGS 00h MEMORY DATA (8 to 24 Bytes)
Response Data for the Read Multiple Blocks Command (No Error, Option_flag Set)
RESPONSE FLAGS 00h SECURITY STATUS (1 Byte) Repeated as needed MEMORY DATA (8 Bytes)
Request Data for the Custom Read Block
REQUEST FLAGS (1 Byte) COMMAND A4h MFG CODE 2Bh UID (8 Bytes) BLOCK NUMBER (1 Byte)
Response Data for the Custom Read Block (No Error, Option_flag Not Set)
RESPONSE FLAGS 00h MEMORY DATA (8 Bytes) INTEGRITY BYTES (2 Bytes)
Response Data for the Custom Read Block (No Error, Option_flag Set)
RESPONSE FLAGS 00h SECURITY STATUS (1 Byte) MEMORY DATA (8 Bytes) INTEGRITY BYTES (2 Bytes)
Read Multiple Blocks
The Read Multiple Blocks command allows for retrieving the data of up to three memory blocks. This command uses two command-specific parameters, which are the starting block number and the number of blocks to read. Valid starting block numbers are 00h to 11h. Permissible number of block values are 0, 1, and 2, corresponding to 1, 2, and 3 blocks. A request that attempts reading beyond block number 11h generates a response with error code 10h. If the Option_flag bit is set, the response includes the block's security status. The security status codes are the same when reading single blocks. See the Read Single Block section for more details.
Custom Read Block
The Custom Read Block command allows for retrieving the data of a single memory block. This command uses one command-specific parameter, which is the memory block number. Valid block numbers are 00h to 11h. If the Option_flag bit is set, the response includes the block's security status. The security status codes are the same as when reading single blocks. See the Read Single Block section for more details.
18
______________________________________________________________________________________
ISO 15693-Compliant 1Kb Memory Fob
Request Data for the Write AFI Command*
REQUEST FLAGS (1 Byte) COMMAND 27h UID (8 Bytes) AFI VALUE (1 Byte)
MAX66120
*If this command is processed without any error, the slave responds with a response flags byte of 00h.
Request Data for the Lock AFI Command
REQUEST FLAGS (1 Byte) COMMAND 28h UID (8 Bytes)
*If this command is processed without any error, the slave responds with a response flags byte of 00h.
Request Data for the Write DSFID Command
REQUEST FLAGS (1 Byte) COMMAND 29h UID (8 Bytes) DSFID VALUE (1 Byte)
*If this command is processed without any error, the slave responds with a response flags byte of 00h.
Request Data for the Lock DSFID Command
REQUEST FLAGS (1 Byte) COMMAND 2Ah UID (8 Bytes)
*If this command is processed without any error, the slave responds with a response flags byte of 00h.
Write AFI
The Write AFI command writes the AFI byte and reports the success of the operation in the response. The AFI byte can alternatively be defined by writing to the proper location in memory block 10h using the Write Single Block command.
Lock DSFID
The Lock DSFID command permanently locks (write protects) the DSFID byte and reports the success of the operation in the response. Before using the Lock DSFID command, the DSFID byte should be written to the device using the Write DSFID command. The DSFID byte can alternatively be locked by writing the DSFID lock byte in memory block 11h to AAh, using the Write Single Block command.
Lock AFI
The Lock AFI command permanently locks (write protects) the AFI byte and reports the success of the operation in the response. Before using the Lock AFI command, the AFI byte should be written to the device using the Write AFI command. The AFI byte can alternatively be locked by writing the AFI lock byte in memory block 11h to AAh, using the Write Single Block command.
CRC Generation
The ISO 15693 standard uses a 16-bit CRC, generated according to the CRC-16-CCITT polynomial function: X16 + X12 + X5 + 1 (see Figure 17). This CRC is used for error detection in request and response data packets and is always communicated in the inverted form. After all data bytes are shifted into the CRC generator, the state of the 16 flip-flops is parallel-copied to a shift register and shifted out for transmission with the LSb first. For more details on this CRC, refer to ISO/IEC 15693-3, Annex C.
Write DSFID
The Write DSFID command writes the DSFID byte and reports the success of the operation in the response. The DSFID byte can alternatively be defined by writing to the proper location in memory block 10h using the Write Single Block command.
______________________________________________________________________________________
19
ISO 15693-Compliant 1Kb Memory Fob MAX66120
MSb POLYNOMIAL = X16 + X12 + X5 + 1
1ST STAGE X0 X1
2ND STAGE X2
3RD STAGE X3
4TH STAGE X4
5TH STAGE X5
6TH STAGE X6
7TH STAGE X7
8TH STAGE
LSb 9TH STAGE X8 X9 10TH STAGE X10 11TH STAGE X11 12TH STAGE X12 13TH STAGE X13 14TH STAGE X14 15TH STAGE X15 INPUT DATA 16TH STAGE X16
Figure 17. CRC-16-CCITT Generator
Command-Specific ISO 15693 Communication Protocol--Legend
SYMBOL GSY WSB LBL RSB RMB CRB WAFI LAFI WDSF LDSF SOF RQF CRC-16 EOF RSF DESCRIPTION Command "Get System Information" Command "Write Single Block" Command "Lock Block" Command "Read Single Block" Command "Read Multiple Blocks" Command "Custom Read Block" Command "Write AFI" Command "Lock AFI" Command "Write DSFID" Command "Lock DSFID" Start of Frame Request Flags byte (always sent by master) Transmission of an inverted CRC-16 (2 bytes) generated according to CRC-16-CCITT End of Frame Response Flags byte (always sent by slave) The tag's unique 8-byte identification number; could be sent by either the master or the slave. The brackets [ ] indicate that the transmission of the UID depends on the request flags (RQF). ICR MFG ERRC BN BDATA MDATA SECS SBN #BLK INTB SYMBOL IFLG DSFID AFI NBLK MBS DESCRIPTION Info Flags byte (always sent by slave) Data Storage Format Identifier byte Application Family Identifier byte Number of Blocks byte (slave memory size indicator) Memory Block Size byte (slave memory block size) IC Reference byte (slave chip revision) Manufacturer Code byte (2Bh) Error Code byte (see Table 5) New Block Data (8 bytes) Buffer Data (8 bytes) Memory Data (8 bytes) Block Security Status byte Starting Block Number byte Number of Blocks to Read byte 2 Integrity bytes (block write cycle counter)
[UID]
20
______________________________________________________________________________________
ISO 15693-Compliant 1Kb Memory Fob
Command-Specific ISO 15693 Communication Protocol--Color Codes
Master-to-Slave Slave-to-Master Programming
MAX66120
ISO 15693 Communication Examples
Get System Information
SOF RQF GSY [UID] CRC-16 EOF (Carrier) SOF RSF = 00h IFLG UID DSFID AFI NBLK MBS ICR CRC-16 EOF
Success
Write Single Block
SOF RQF WSB [UID] BN BDATA CRC-16 EOF (Carrier) tPROG SOF RSF = 00h CRC-16 EOF
Success Error
SOF RSF = 01h ERRC CRC-16 EOF
Lock Block
SOF RQF LBL [UID] BN CRC-16 EOF (Carrier) tPROG SOF RSF = 00h CRC-16 EOF
Success Error
SOF RSF = 01h ERRC CRC-16 EOF
Read Single Block
SOF RQF RSB [UID] BN CRC-16 EOF (Carrier) SOF RSF = 00h MDATA CRC-16 EOF SOF RSF = 00h SECS MDATA CRC-16 EOF SOF RSF = 01h ERRC CRC-16 EOF
Success
(Option_Flag = 0)
Success
(Option_Flag = 1)
Error
______________________________________________________________________________________
21
ISO 15693-Compliant 1Kb Memory Fob MAX66120
ISO 15693 Communication Examples (continued)
Read Multiple Blocks
SOF RQF RMB [UID] SBN #BLK CRC-16 EOF (Carrier) MDATA CRC-16 EOF (1, 2, or 3 blocks) SECS AND MDATA CRC-16 EOF (1, 2, or 3 blocks)
Success
(Option_Flag = 0)
SOF RSF = 00h
Success
(Option_Flag = 1)
SOF RSF = 00h
Error
SOF RSF = 01h ERRC CRC-16 EOF
Custom Read Block
SOF RQF CRB MFG [UID] BN CRC-16 EOF (Carrier) SOF RSF = 00h MDATA INTB CRC-16 EOF SOF RSF = 00h SECS MDATA INTB CRC-16 EOF SOF RSF = 01h ERRC CRC-16 EOF
Success
(Option_Flag = 0)
Success
(Option_Flag = 1)
Error
Write AFI
SOF RQF WAFI [UID] AFI CRC-16 EOF (Carrier) tPROG SOF RSF = 00h CRC-16 EOF
Success Error
SOF RSF = 01h ERRC CRC-16 EOF
Lock AFI
SOF RQF LAFI [UID] CRC-16 EOF (Carrier) tPROG SOF RSF = 00h CRC-16 EOF
Success Error
SOF RSF = 01h ERRC CRC-16 EOF
22
______________________________________________________________________________________
ISO 15693-Compliant 1Kb Memory Fob
ISO 15693 Communication Examples (continued)
Write DSFID
SOF RQF WDSF [UID] DSFID CRC-16 EOF (Carrier) tPROG SOF RSF = 00h CRC-16 EOF
MAX66120
Success Error
SOF RSF = 01h ERRC CRC-16 EOF
Lock DSFID
SOF RQF LDSF [UID] CRC-16 EOF (Carrier) tPROG SOF RSF = 00h CRC-16 EOF
Success Error
SOF RSF = 01h ERRC CRC-16 EOF
Key Fob Mechanical Drawing
TOP VIEW
54mm
28mm
7.7mm
MAX66120K-000AA+
1.6mm
SIDE VIEW
______________________________________________________________________________________
23
ISO 15693-Compliant 1Kb Memory Fob MAX66120
Revision History
REVISION NUMBER 0 REVISION DATE 11/10 Initial release DESCRIPTION PAGES CHANGED --
Maxim cannot assume responsibility for use of any circuitry other than circuitry entirely embodied in a Maxim product. No circuit patent licenses are implied. Maxim reserves the right to change the circuitry and specifications without notice at any time.
24 ____________________Maxim Integrated Products, 120 San Gabriel Drive, Sunnyvale, CA 94086 408-737-7600 (c) 2010 Maxim Integrated Products Maxim is a registered trademark of Maxim Integrated Products, Inc.

▲Up To Search▲

Price & Availability of MAX66120

	To Download MAX66120 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .